Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.
TITLE: Server Optimization and Functions
DOCUMENT ID#: FYI.P.6037
DATE: October 29, 1991
PRODUCT: NetWare Lite
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Server Optimization and Functions
Disk Caches
NetWare Lite does not ship with a disk cache. We have tested with several (read many) commercially available disk cache products and found them to be quite inexpensive while adding significant performance to the NetWare Lite server software. We suggest for higher performance of the NetWare Lite server that a disk cache be acquired and installed on the server machines. Some cache tuning may be necessary for best results.
Server Configuration
For best performance we suggest that receive buffer and read buffer sizes be increased to what is supported by the network topology (i.e. ethernet, token ring) up to a maximum of 4096 bytes using a multiple of 512 bytes. In fact, if 4096 is selected then the server will truncate the value to the maximum value supported by the topology. This tuning allows clients to request more data from (or send more data to) the server with each read (write) operation. When more data is sent, fewer requests are necessary and better performance is obtained. This enhancement does increase the size of SERVER when it is resident in DOS.
Depending on the "load" being placed on the server, it may be beneficial to increase the number of receive buffers and read buffers. In general, we have found that 8-12 receive buffers is enough for even the most heavily loaded server. Similarly, 5-10 read buffers is sufficient. These values need not be more than one or two above the number of simultaneous connections (up to our suggested maximums of 8-12 receive buffers and 5-10 read buffers).
Mapping vs. SUBSTing
If your machine is a server and you would like to map to yourself, it is recommended that you SUBST to yourself instead of mapping to yourself. SUBST is a DOS command that lets you assign a drive letter to a directory on another drive. For example, if you usually map to yourself with G: to the Network Directory APPS, and if APPS is actually the C:\APPS directory, the NET MAP G: APPS could be replaced by SUBST G: C:\APPS. To remove this substitution, you would type SUBST G: /D. Using this substitution, rather than a mapping, will result in better performance for operations done on drive G:.
Mapping Local Drive
You can map drives that are local, for example A: or B:, and use them temporarily as network drives. However as a general practice, it is not recommended. If you run out of drive letters to map, increase LASTDRIVE in your CONFIG.SYS.
Use of ASSIGN
Do not use ASSIGN with NetWare Lite. The DOS reference manual (3.3) recommends that you use SUBST instead of ASSIGN and explains how to do so.
